Micron Document
┏┳┓┏┓┏┓┳┏┓┏┓╻ ┏┳┓┓┏┏┓ ┳┓┏┓┳┳┓┏┓┳┓ ┏┓┏┓┳┓┳┳┳┳┓
┃ ┃┃┃┃┃┃ ┗┓┃ ━━ ┃ ┣┫┣ ┃┃┃┃┃┃┃┣┫┃┃ ┣ ┃┃┣┫┃┃┃┃┃
┻ ┗┛┣┛┻┗┛┗┛• ┻ ┛┗┗┛ ┛┗┗┛┛ ┗┛┗┻┛ ┻ ┗┛┛┗┗┛┛ ┗
You are logged as: Guest User Status: Read Only Mode // Identify or Fingerprint to write new Posts!


Title: What we should do with RNS Author: socrates Posted the: 01 Nov 2025 03:25 Category: Reticulum

What we should do with RNS

figure out group chat LXMF and build it (why no one uses distribution groups?)
make other programs on top of RNS in addition to nomadnet (I have idea for this)
red teaming
make an IFAC based network as alternative to the test net. like test net 2. will they just blend together? Is IFAC just for interfaces? I think so. Can RNS nets be segregated?
make cool programs and share them

👁️ 649 Views - 💬 24 Replies - ❤️ 2 Like
━━━ ARTICLE REPLIES: (24) ━━━

Author: Franky · Posted: 01 Nov 2025 10:10 · ❤️ 1
Reply: hey socrates! i don't know if its possible to create group chat with lxmf, its a p2p protocol on top of the rns stack, so 1 to 1 chat only for now otherwise the author would have already implemented it i think. the alternatives are as you said the distribution groups, or the chatroom for nomadnet at the moment, someone has the distribution groups active, just do a research in the announces, you could host your own also. the testnet are the public tcp servers, you can host your private rnsd and make it closed. ifac is to limit access only to wanted users to create a sort of private network. reticulum is an open source project and involve the commnunity to build things on it...if something doesn't exist yet, you could try to DIY create it or wait that someones build it!
Author: socrates · Posted: 01 Nov 2025 21:20 · ❤️ 1
Reply: I started re-writing rnpath to learn more about RNS to build stuff on it. TBQH the code is missing some elegance. It makes me wonder what else is lurking in the RNS implementation
Author: Franky · Posted: 02 Nov 2025 12:08 · ❤️ 1
Reply: does the rnpath -r (rates) command works on your machine? i never get replies from it, always: No information available
Author: socrates · Posted: 03 Nov 2025 17:30 · ❤️ 0
Reply: It means the RNS.Transport.announce_rate_table is an empty dictionary. I'm not sure what its purpose is. But it's not being populated on my node.
Author: socrates · Posted: 03 Nov 2025 17:38 · ❤️ 0
Reply: It means the RNS.Transport.announce_rate_table is an empty dictionary. I'm not sure what its purpose is. But it's not being populated on my node.
Author: socrates · Posted: 03 Nov 2025 17:40 · ❤️ 1
Reply: sorry for double post. it seems the announce rate table is only populated if an interface has an "announce_rate_target" parameter set to an integer.
Author: Frank_ · Posted: 03 Nov 2025 17:51 · ❤️ 1
Reply: ahh okk understood!! so no announce_rate_target = no info available from command, tnx!
Author: Lia · Posted: 19 Jan 2026 02:09 · ❤️ 0
Reply: I believe group chats should be possible by implementing a feature on LXMF where you can simply group messages into a channel in the front-end, but in the backend it just individually sends the same message for everyone inside the group channel + an identifier telling LXMF that this message goes to X group channel
Author: Lia · Posted: 19 Jan 2026 02:10 · ❤️ 0
Reply: so its closer to an email CC group, but gets displayed as a group chat
Author: rBrowser · Posted: 22 Jan 2026 17:13 · ❤️ 1
Reply: hey lia, for this solution we already have "lxmf distribution groups" , lxmf-cli group chat plugin , rth group chat and more, but its a sort of hack, not a real group chat due to the p2p nature of lxmf. there is also the chatroom on nomadnet.
Author: hobo · Posted: 17 Feb 2026 04:55 · ❤️ 0
Reply: I've been contemplating what a distributed IRC might look like in RNS/LXMF, the RRC is pretty good but ephemerial. If a persistant dRRC node listend for other dRRC nodes, swapping public room lists. Each local node could distribute to peers who participated. It could use LXMF for sharing messages, but user/lurkers would be responsible for keeping their own logs.
Author: Scooter · Posted: 22 Feb 2026 17:36 · ❤️ 0
Reply: I'm new to this, but I don't quite understand why you can't do group messages in LXMF. Reticulum docs say there is support for group destinations. Wouldn't this provide the infra to build group chats?
Author: hobo · Posted: 23 Feb 2026 05:52 · ❤️ 0
Reply: It's not my expertise, but encryption and groups is tricky, usually requiring a 3rd party or something that compromises the intent.
Author: TheCleric · Posted: 25 Feb 2026 16:16 · ❤️ 2
Reply: Content warning NOOB: I feel like forums are 90% of the way there to group chats. Couldn't you set up a forum with white-listed fingerprints to view and post? and then wrap it nicely. The main problem is it creates a bit of friction as having a group-chat would require hosting pages.
Author: servant · Posted: 28 Feb 2026 16:08 · ❤️ 1
Reply: I think we need to make RNS a little bit profitable to boost the development of the ecosystem... Maybe descentralized forums cacn be made with a blockchain-like approach?
Author: shades · Posted: 11 Mar 2026 21:29 · ❤️ 0
Reply: servant, i was talkin to a friend and i'm not sayin i want to do this, but rns would pop off if it had it's own silk road lol. something profit driven that's only accessible via rns. once again, i'm not doin that, just thought it was funny that that's what it would take
Author: shades · Posted: 11 Mar 2026 21:30 · ❤️ 0
Reply: i have also thought about the group-message shaped hole in rns, and do think it's just a matter of nice ui. maybe torlando could add something like it to columba
Author: shades · Posted: 11 Mar 2026 21:31 · ❤️ 0
Reply: other ideas i had, 1. adapting something like activitypub to rns, 2. adapting bittorrent
Author: Felucca · Posted: 12 Mar 2026 20:21 · ❤️ 0
Reply: New to this but I agree with @TheCleric. People want decentralized everything and that's not really the point. Even in decentralization you need to build some form of trust with apps/third parties. The difference is you are now accessing them via a decentralized network. At is base RNS is fine in its current implementation. I am not aware of anything breaking the system or hitting maxes yet. If anyone has additional information into these events please educate us!
Author: Felucca · Posted: 12 Mar 2026 20:25 · ❤️ 0
Reply: IMO we need to get all these idle meshtastic devices to become rnodes. Meshtastic has a very small range of hops allowed. RNodes are the solution to this. Recently saw a person comment about a 100+ hop over rnodes on reticulum. I would love to see that in the wild implementation!
Author: Soupbones · Posted: 14 Mar 2026 22:05 · ❤️ 0
Reply: Reticulum could easily be the future of LorA mesh networks and take over both Meshtastic and Meshcore just because of the more advanced usage we have with RNS. But you will need to attarct more common users. This means takign a leaf from the book of Meshcore and create a simple way to flash a node for a specific job. Also expand the amount of devices available to be flashed. It is still very limited. Set up a portal where its very simple to flash hardware for Rnode or TNC usage. The more 'KISS thoery that is applied to Reticulum to make it more usable to the common man, the more people will jump on the bandwagon and increase the mesh. Currently the attitude is to not do this, to have CLI involved with everyday simple tasks across RNS. These discourage new users greatly.
Author: ALA01 · Posted: 18 Mar 2026 01:08 · ❤️ 0
Reply: I think an iOS app will be a major milestone for reticulum. Sideband or meshchat or whatever.
Author: txbluebonnet · Posted: 14 Apr 2026 11:30 · ❤️ 0
Reply: To all those who are helping out with the code, thank you! Although there are a lot of quirks, bugs, etc., everything seems very promising!
Author: petestillman · Posted: 31 May 2026 02:16 · ❤️ 0
Reply: ascii videocalls - superior to MS Teams because (very) low bandwidth and power consumption, anonymous/masked, no need of filters. I've made an example with hasciicam at cdfa7292616244aff682bdcc073ef161:/page/index.mu and would be grateful for any help to test a python viewer-script

You must be logged in to post replies. Please identify or fingerprint to NomadNet.